home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950528-19950726
/
000122_news@columbia.edu_Mon Jun 12 04:42:48 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA10566
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 12 Jun 1995 14:01:56 -0400
Received: by apakabar.cc.columbia.edu id AA24313
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 12 Jun 1995 14:01:54 -0400
Path: news.columbia.edu!panix!news.mathworks.com!news.ultranet.com!news.sprintlink.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Help! Kermit 3.1.4 makes my Windows 3.1 apps crash!
Message-Id: <1995Jun12.104248.53890@cc.usu.edu>
Date: 12 Jun 95 10:42:48 MDT
References: <3rhk95$l5@elna.ethz.ch>
Distribution: world
Organization: Utah State University
Lines: 31
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3rhk95$l5@elna.ethz.ch>, FUTTERBAU@cumuli.vmsmail.ethz.ch (Frehner Marco) writes:
> Hello
>
> I've been using Kermit for a while and with version 3.1.3 thing normally worked
> quite well. Except for occasional crashes of otherwise well-behaved programs
> (MS-Winword 2.0, MS-Excel 5.0) when Kermit was doing a file-transfer in the
> background.
> However, after upgrading to Kermit 3.1.4 (and using 2000 character packets),
> things got a lot worse.
> I cannot work anymore during a file transfer as there will be random GPF's in
> Winword and errors similar to "Cannot load ANYDLL.DLL" in Excel.
> My Computer is an IBM PS/VP 433DX (33 MHz, 20 MB Ram) running MS-Dos 5.02 and
> MS-Windows 3.1. I am running Kermit over a direct link (using a T-box and
> broadband communications) to a VAX server.
>
> Has anyone experienced similar problems? I would greatly appreciate any hints.
------------
Welcome to Windows, a hostile land for any communications process.
It's not Kermit itself, but rather some combination of ingredients in your
PC. Lovely. We can't diagnose the many ills that involve Windows, of course,
but the best that I can suggest is a) review your memory management with
a very careful eye to detail, and b) don't expect the stock Windows comm
driver to work much above 9600 bits/sec. If you've fallen victim to using
Smartdrive then remove it since it turns off cpu recognition of interrupts
when it does buffer flushes. Screen savers are another gotcha waiting to
strike.
Finally, please do take note of Kermit's use of EXPANDED memory
for screen rollback buffers. We discuss that in the release documentation.
Good luck with the investigation, and you have plenty of company
with Windows GPF's from any cause.
Joe D.